@mitu Sorry for the late reply, gave both of these a shot and it still displayed a black screen on the RaspiConfig

I also just tried group 63 for 1080P with 120HZ and got the same result

@mitu I transplanted the configurations from a newly installed Retropie card to my existing installation, and have lr-atari800 working again.

Thanks

@duiz Here is my idea for fixing your resolution problem.

Firstly, try this.

Change this:

#disable_overscan=1

To this:
disable_overscan=1

Reset and see if that fixes it.

If that doesn't work change this :
#framebuffer_width=1280
#framebuffer_height=720

To this :
framebuffer_width=1920
framebuffer_height=1080

Make sure to remove the # before those lines.

If it doesn't work be sure to put it back the way it was.

Hopefully one of those ideas helps.

@CobraKai I have not, but it looks like the xow driver is only for use with the Xbox wireless dongle. (I think it only references bluetooth on the 'supported devices' frame to differentiate it from the the other models)

Hi @asksolutions01 !

It was fixed using the information in the thread above. I had to disable the EDID detection and add manual configuration settings on my display via the config file.

This is also the info from the online documentation:

hdmi_ignore_edid
Setting hdmi_ignore_edid to 0xa5000080 enables the ignoring of EDID/display data if your display does not have an accurate EDID. It requires this unusual value to ensure that it is not triggered accidentally.

Link to the documentation website

@andyng Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Your install sounds very out of date. But can't advise without more information apart from to update to a newer version - also 16.04 is probably too old now to work. Recommend 18.04 or 20.04

if it's screensaver / screenblanking shouldn't it happen when other screens are attached as well ? the settings about it do not change when switching screens so in theory he should have the issue on every screen attached then

You might want to change the font to something bigger (xterm -fn <fontname>) if your resolution will make the fonts tiny.

@mitu when the crash happen, i hard reset then restart the system as i can't get a tty in a freeze status.. so i go like you suggest me to get log from /dev/shm/runcommand.olg but i can't find nothing. infact as sometime get no crash i find there the log without error as a list the operation in the retropie like type of emulator rom launched etc. so crash without log or log without crash.
i can't go further..infact i can't understand what happened different when one time things go perfect ( sometime i change the kernel ... but second chances to run other rom all crash so i think is not depending on this ) i don't know if depend on using a particular type of emulator : neo geo or version of mame and i don't know, it's own configuration ( video settings, audio .. ) but i can't get log after crash ... so i dont know to proceed to fix. have a nice day and thnx for all the detailed reply.

@mitu I wiped my ds card and redownloaded RetroPie everything is good now

@mausiemaup Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@buzz is there any other way to have RetroPie on a multi boot? I would like to have different images of Retropie with different setups, without swapping different ssd every time.

I don't think mirroring would work, since the displays are of different resolutions. I think you can make the HDMI the primary display by adding display_default_lcd=0 to the config.txt, so if HDMI is detected, then the primary output would be switched to it.

@ULTRA-MAGNUSS I found a solution to Cobra Command on my own. Use cobram3.zip as your rom. cobra.zip and cobraab doesn't seem to work. Create a cobram3.daphne folder with the frame file, video files, and sound file in the daphe folder. If you already have .dat files in your cobram3.daphne folder, delete just the .dat files. Once you try to run the game it should parse your video and then should be ready to play. I'm so happy I got it working. Now I gotta figure out how to remap the controls.

It works!
TBH this project required a little more than that. Had to uncomment a line in a config file to make the screen come to life. Had to change default keyboard layout (I'm using US keyboard, couldn't type "|"). Had to localize system. Had to install gamepad driver and configure input. Mount system on my network. And of course install a romset in the proper directory. Still... WORTH IT.

Thanks for your help.

So apparently I'm an idiot. Following the guide over at Reddit, I missed one thing. I had the mini-hdmi cable plugged into the second port and not to the port closest to the power supply. Looks like everything is working now.

@misterbo42 said in Black screen after few minutes of gaming:

I don’t know where I can find a log of these errors but if someone can tell me I would look at it.

The runtime log is usually in /dev/shm/runcommand.log. You can also try running dmesg from the command line after this happens to see if any warning/errors are shown in the system log.

Can you give more details - as asked in https://retropie.org.uk/forum/topic/3/read-this-first ? Which emulator, what RetroPie version (don't say latest), how did you install it, etc.

Does it happen for all games or just for a particular game/system ? Did you overclock your PI ?

Well, glad you got it set-up. Enjoy playing with your RetroPie !

The Pi4 is not supported by RetroPie yet - either with the image(s) provided on the download page or through the manual installation (over Raspbian).